Skip to content

Conversation

@Mossaka
Copy link
Member

@Mossaka Mossaka commented Feb 18, 2025

This SKIP adds support for Azure Workload Identity to spin operator.

CC @devigned


Proot of concept:

spinframework/spin-operator#372

Signed-off-by: Jiaxiao (mossaka) Zhou <[email protected]>
Mossaka added a commit to Mossaka/spin-operator-msk that referenced this pull request Feb 21, 2025
This adds a new 'workloadIdentity' field to the SpinApp CRD and the controller will detect this field to
determine whether or not to apply provider specific labels to enable cloud workload identity.

See SKIP spinframework/skips#16 for more details

Signed-off-by: Jiaxiao (mossaka) Zhou <[email protected]>
Mossaka added a commit to Mossaka/spin-operator-msk that referenced this pull request Mar 6, 2025
This adds a new 'workloadIdentity' field to the SpinApp CRD and the controller will detect this field to
determine whether or not to apply provider specific labels to enable cloud workload identity.

See SKIP spinframework/skips#16 for more details

Signed-off-by: Jiaxiao (mossaka) Zhou <[email protected]>
…rent implementation

Signed-off-by: Jiaxiao (mossaka) Zhou <[email protected]>
workloadIdentity:
serviceAccountName: "workload-identity-sa"
providerMetadata:
azure: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this seems reasonable - do we have a sense of what alternative cloud workload identity would look like here? (I haven't spent a huge amount of time on cloud k8s since these became common, so don't have good intuition about what EKS/GKE would look like)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants